Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce4ffe0b2e6511ed079f26e7160b9a782e3fb8b34bc7775326d4dafbb59097ad

Tx prefix hash: 8ea9c2c9807ee4bc55cd5242b0405e64a81eda8854a1860e35bece841c24bce7
Tx public key: f64b414994d8c7f336121e412d913f4146c32125e93e5e2cd60cd55cde2e81bb
Timestamp: 1733836182 Timestamp [UCT]: 2024-12-10 13:09:42 Age [y:d:h:m:s]: 00:102:17:25:19
Block: 1172170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73198 RingCT/type: yes/0
Extra: 01f64b414994d8c7f336121e412d913f4146c32125e93e5e2cd60cd55cde2e81bb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34065c8f19e4c40e70e97db705a9941eada68fd772b026452f7c246454967422 0.600000000000 1658027 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": 1172180, "vin": [ { "gen": { "height": 1172170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34065c8f19e4c40e70e97db705a9941eada68fd772b026452f7c246454967422" } } ], "extra": [ 1, 246, 75, 65, 73, 148, 216, 199, 243, 54, 18, 30, 65, 45, 145, 63, 65, 70, 195, 33, 37, 233, 62, 94, 44, 214, 12, 213, 92, 222, 46, 129, 187, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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