Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d470195b0a32ce10a0964f7855c6854ae0dacd73e005949a40a7237f11da3416

Tx prefix hash: bcada4a4dd3ea03b08e7f1a05635c819a4a89b62687180588b5434a32f701026
Tx public key: 8e952020bb04215e90c6b2a83e7ba2e670d28c1d4fce861fa2e1dac71eff09bf
Timestamp: 1733359791 Timestamp [UCT]: 2024-12-05 00:49:51 Age [y:d:h:m:s]: 00:159:08:33:20
Block: 1168215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113719 RingCT/type: yes/0
Extra: 018e952020bb04215e90c6b2a83e7ba2e670d28c1d4fce861fa2e1dac71eff09bf0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d55bca97adb9a9d85a1176dcd334fd69d75ad1d969f04bc36ea0c779d21aa4 0.600000000000 1653922 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": 1168225, "vin": [ { "gen": { "height": 1168215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d55bca97adb9a9d85a1176dcd334fd69d75ad1d969f04bc36ea0c779d21aa4" } } ], "extra": [ 1, 142, 149, 32, 32, 187, 4, 33, 94, 144, 198, 178, 168, 62, 123, 162, 230, 112, 210, 140, 29, 79, 206, 134, 31, 162, 225, 218, 199, 30, 255, 9, 191, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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