Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bfe297c1ff1e2aed8430d142745f6592cf0b2ab1c292dfee89eeefa83d682df9

Tx prefix hash: b00f48254c54a306991ea26dfda136e089ece913f0d62f54659634307b3ff1c7
Tx public key: aefe92a7c0aada6fa3b736b7a7bcd82c1246ee165f02ec30fb3f9a9536ddf493
Timestamp: 1706769628 Timestamp [UCT]: 2024-02-01 06:40:28 Age [y:d:h:m:s]: 01:276:14:54:51
Block: 947851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456480 RingCT/type: yes/0
Extra: 01aefe92a7c0aada6fa3b736b7a7bcd82c1246ee165f02ec30fb3f9a9536ddf49302110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10c682092b9009cb7be6e8c65814946740c5233ebab2d7dc36360f4326d57bdb 0.600000000000 1406209 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 947861, "vin": [ { "gen": { "height": 947851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10c682092b9009cb7be6e8c65814946740c5233ebab2d7dc36360f4326d57bdb" } } ], "extra": [ 1, 174, 254, 146, 167, 192, 170, 218, 111, 163, 183, 54, 183, 167, 188, 216, 44, 18, 70, 238, 22, 95, 2, 236, 48, 251, 63, 154, 149, 54, 221, 244, 147, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8