Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c734fd17e29ecc6e94be78086d63d97ef5c3e3169e1b459afbb51efea78d605c

Tx prefix hash: 661e7d7da6c1235c12d2e89bd89f15fded6e33461bc8b673eb747087b0b9666c
Tx public key: 4e6278bb51e4b237bdfb1b70ac81fc8ca5fa39847097eb22387381fca840f066
Timestamp: 1632739660 Timestamp [UCT]: 2021-09-27 10:47:40 Age [y:d:h:m:s]: 03:174:08:32:02
Block: 341804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 901100 RingCT/type: yes/0
Extra: 014e6278bb51e4b237bdfb1b70ac81fc8ca5fa39847097eb22387381fca840f06602110000000f36fe6557000000000000000000

1 output(s) for total of 45.233676786000 dcy

stealth address amount amount idx
00: 310ea10102b1304f466dca630dd0b957be9be2f441f2fa5e3d46a90105f7a6c3 45.233676786000 702132 of 0

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": 341814, "vin": [ { "gen": { "height": 341804 } } ], "vout": [ { "amount": 45233676786, "target": { "key": "310ea10102b1304f466dca630dd0b957be9be2f441f2fa5e3d46a90105f7a6c3" } } ], "extra": [ 1, 78, 98, 120, 187, 81, 228, 178, 55, 189, 251, 27, 112, 172, 129, 252, 140, 165, 250, 57, 132, 112, 151, 235, 34, 56, 115, 129, 252, 168, 64, 240, 102, 2, 17, 0, 0, 0, 15, 54, 254, 101, 87, 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