Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc79e18ea0f066901800b0aee488e52c97cf65a51895a06267200ded8f51a2e

Tx prefix hash: afd43a698ee933530eb3a228896cd8f7fab78fe515778eeadaa5f99f4e7199c1
Tx public key: da0e027977c2b0f2e27fb6d7e270b11d94b3917d547dd42d24883a6d2717eaf2
Timestamp: 1705542572 Timestamp [UCT]: 2024-01-18 01:49:32 Age [y:d:h:m:s]: 01:118:15:28:30
Block: 937665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345931 RingCT/type: yes/0
Extra: 01da0e027977c2b0f2e27fb6d7e270b11d94b3917d547dd42d24883a6d2717eaf202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49a771f407842c0289d66cf2815b74cf27663ca8cb91a782df2c41fd42bcce38 0.600000000000 1395727 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": 937675, "vin": [ { "gen": { "height": 937665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49a771f407842c0289d66cf2815b74cf27663ca8cb91a782df2c41fd42bcce38" } } ], "extra": [ 1, 218, 14, 2, 121, 119, 194, 176, 242, 226, 127, 182, 215, 226, 112, 177, 29, 148, 179, 145, 125, 84, 125, 212, 45, 36, 136, 58, 109, 39, 23, 234, 242, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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