Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5171f2ca836c240437791d7cf98201736c28811b70b55ef4aa8a905992134e76

Tx prefix hash: 99591eec0ae625c22b9cda9d44fedf0e7b8c18a4075edf94100ae69dc784f64a
Tx public key: 2e1271a78602d5519fec2d8ad94d4c21f5b737db1db054d6a3b722641f6e2c3c
Timestamp: 1703779004 Timestamp [UCT]: 2023-12-28 15:56:44 Age [y:d:h:m:s]: 01:145:05:12:30
Block: 923076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364941 RingCT/type: yes/0
Extra: 012e1271a78602d5519fec2d8ad94d4c21f5b737db1db054d6a3b722641f6e2c3c021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b4e590ad1b34e478e95bb2e3cea6be63fa684be3ec32c3073af4982bcf4867c 0.600000000000 1380794 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": 923086, "vin": [ { "gen": { "height": 923076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b4e590ad1b34e478e95bb2e3cea6be63fa684be3ec32c3073af4982bcf4867c" } } ], "extra": [ 1, 46, 18, 113, 167, 134, 2, 213, 81, 159, 236, 45, 138, 217, 77, 76, 33, 245, 183, 55, 219, 29, 176, 84, 214, 163, 183, 34, 100, 31, 110, 44, 60, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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