Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9a1114202803a6ed6a61af291076948a430c961616152b91abba9fbd9d1970

Tx prefix hash: c3a6ad147fae92efd35e2d574874bb9a0edb2e5f0223645aa4b7be1209eb3f6a
Tx public key: 90d84d8c71f76d318af3ab6de43d6bb20cbbfb02ed1902115333fb540854909e
Timestamp: 1657018953 Timestamp [UCT]: 2022-07-05 11:02:33 Age [y:d:h:m:s]: 02:224:07:46:25
Block: 537117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 681441 RingCT/type: yes/0
Extra: 0190d84d8c71f76d318af3ab6de43d6bb20cbbfb02ed1902115333fb540854909e0211000000394da16a3a000000000000000000

1 output(s) for total of 10.193153451000 dcy

stealth address amount amount idx
00: 0c219ea8fb2f6c104a9e6337b6c223ac11eb96160c134c8b290622e041ae1f65 10.193153451000 966974 of 0

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": 537127, "vin": [ { "gen": { "height": 537117 } } ], "vout": [ { "amount": 10193153451, "target": { "key": "0c219ea8fb2f6c104a9e6337b6c223ac11eb96160c134c8b290622e041ae1f65" } } ], "extra": [ 1, 144, 216, 77, 140, 113, 247, 109, 49, 138, 243, 171, 109, 228, 61, 107, 178, 12, 187, 251, 2, 237, 25, 2, 17, 83, 51, 251, 84, 8, 84, 144, 158, 2, 17, 0, 0, 0, 57, 77, 161, 106, 58, 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