Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfede2e384088eac2c189e68cea4a1be420c7742f255fc651f071e4d1d1aae85

Tx prefix hash: 7693b7a193b13a802d20436d0745ae3b87cf7db916257787c1e93d2542430a4f
Tx public key: 7046297a4a1168630e9255c318903e3dcaea6e3eef491428fce22dfa579d494c
Timestamp: 1738001736 Timestamp [UCT]: 2025-01-27 18:15:36 Age [y:d:h:m:s]: 00:323:11:22:29
Block: 1206396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228967 RingCT/type: yes/0
Extra: 017046297a4a1168630e9255c318903e3dcaea6e3eef491428fce22dfa579d494c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07f0a8a6559edc1a5be9ca758b26743f30b9c2d51c8d2548537fd7e44ca5c55c 0.600000000000 1693101 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": 1206406, "vin": [ { "gen": { "height": 1206396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07f0a8a6559edc1a5be9ca758b26743f30b9c2d51c8d2548537fd7e44ca5c55c" } } ], "extra": [ 1, 112, 70, 41, 122, 74, 17, 104, 99, 14, 146, 85, 195, 24, 144, 62, 61, 202, 234, 110, 62, 239, 73, 20, 40, 252, 226, 45, 250, 87, 157, 73, 76, 2, 17, 0, 0, 0, 4, 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