Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d299da7dbc3cb56026b9594387c2ab8d805533f3c7ff449b203240f4908e6e3b

Tx prefix hash: 4d314a0e1add1e44214e575b23bcbc8ba395d9b61bfb00c01c154471f87118f5
Tx public key: 79e162fb49a1f370ef8a8186cefbfe3bb688109fe30bc51fda1f46e4e497461a
Timestamp: 1720988858 Timestamp [UCT]: 2024-07-14 20:27:38 Age [y:d:h:m:s]: 00:263:12:04:33
Block: 1065764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188242 RingCT/type: yes/0
Extra: 0179e162fb49a1f370ef8a8186cefbfe3bb688109fe30bc51fda1f46e4e497461a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4038522d4b4ecff50499666f87e9cb3021f162ea2d6e3586d6fdfd724eeb515 0.600000000000 1536315 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": 1065774, "vin": [ { "gen": { "height": 1065764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4038522d4b4ecff50499666f87e9cb3021f162ea2d6e3586d6fdfd724eeb515" } } ], "extra": [ 1, 121, 225, 98, 251, 73, 161, 243, 112, 239, 138, 129, 134, 206, 251, 254, 59, 182, 136, 16, 159, 227, 11, 197, 31, 218, 31, 70, 228, 228, 151, 70, 26, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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