Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b5ddce287ad9fb7105fb51898366bd5b0ae580b95eaf29395c00b20f82a7bc8

Tx prefix hash: 63e1fd449dafdf1c9fabd1f27f7df108f80c6ad23220efb1cd08eb625a85de44
Tx public key: 660e8cf6475398ffbc49455d629172480a8bb23330f62a8e331b1b2cff259c97
Timestamp: 1702855707 Timestamp [UCT]: 2023-12-17 23:28:27 Age [y:d:h:m:s]: 01:173:07:30:50
Block: 915425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385040 RingCT/type: yes/0
Extra: 01660e8cf6475398ffbc49455d629172480a8bb23330f62a8e331b1b2cff259c97021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3db0d7a0f2cae880cdff0c3e9bb703584bc61bdb96c3fa0e749763d916127471 0.600000000000 1372821 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": 915435, "vin": [ { "gen": { "height": 915425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3db0d7a0f2cae880cdff0c3e9bb703584bc61bdb96c3fa0e749763d916127471" } } ], "extra": [ 1, 102, 14, 140, 246, 71, 83, 152, 255, 188, 73, 69, 93, 98, 145, 114, 72, 10, 139, 178, 51, 48, 246, 42, 142, 51, 27, 27, 44, 255, 37, 156, 151, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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