Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1144e0f96a8bf4387f82deb64c55d6e965d8a208c7c0a8d836094500fec6da6

Tx prefix hash: 9a362540ca2dc6fb8ec636510764a90c2cd49a3555651333d98ec7587519cbe9
Tx public key: 578d2d304fe83a9dc7123ff42f4ab0fb9885e242124dfbafeffee372f4a9759a
Timestamp: 1702514501 Timestamp [UCT]: 2023-12-14 00:41:41 Age [y:d:h:m:s]: 01:191:17:17:12
Block: 912588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398023 RingCT/type: yes/0
Extra: 01578d2d304fe83a9dc7123ff42f4ab0fb9885e242124dfbafeffee372f4a9759a02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b019aeb483d5b528fc454e16d92333d245b4364f38b625056a8ef295ae274e28 0.600000000000 1369818 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": 912598, "vin": [ { "gen": { "height": 912588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b019aeb483d5b528fc454e16d92333d245b4364f38b625056a8ef295ae274e28" } } ], "extra": [ 1, 87, 141, 45, 48, 79, 232, 58, 157, 199, 18, 63, 244, 47, 74, 176, 251, 152, 133, 226, 66, 18, 77, 251, 175, 239, 254, 227, 114, 244, 169, 117, 154, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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