Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e014713ca4dfa4c3a9247d2a12458928788914c6b85458ed46e6a9b124589851

Tx prefix hash: 00915089c637c69aa3e687876841ebaac0fe729780876cd447b2838a593a78d4
Tx public key: f6f087e20cf0aaad99007fa692a3177b628e745410081e5d98ea3e32e2ac7403
Timestamp: 1706351266 Timestamp [UCT]: 2024-01-27 10:27:46 Age [y:d:h:m:s]: 01:301:17:10:58
Block: 944381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474458 RingCT/type: yes/0
Extra: 01f6f087e20cf0aaad99007fa692a3177b628e745410081e5d98ea3e32e2ac740302110000000710a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c26c1c784124cfd4eae2d802b0655433870d32a5b10575c2d1effc49fd2e1d24 0.600000000000 1402617 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": 944391, "vin": [ { "gen": { "height": 944381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c26c1c784124cfd4eae2d802b0655433870d32a5b10575c2d1effc49fd2e1d24" } } ], "extra": [ 1, 246, 240, 135, 226, 12, 240, 170, 173, 153, 0, 127, 166, 146, 163, 23, 123, 98, 142, 116, 84, 16, 8, 30, 93, 152, 234, 62, 50, 226, 172, 116, 3, 2, 17, 0, 0, 0, 7, 16, 161, 116, 143, 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