Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef08c14a929c4cb67d706968d2cdf38314203e0dba3ad4ebb1f932069eebec27

Tx prefix hash: cf92796435d6364dc24b2ee8d4bb9a50b79ce0712a32c7a3a9f6617bba69de27
Tx public key: e1aea84f3d4cb55c104db13ee39274fd6e551053af5a78531c13bbfb2aa8ceae
Timestamp: 1736365086 Timestamp [UCT]: 2025-01-08 19:38:06 Age [y:d:h:m:s]: 00:162:12:10:36
Block: 1193090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115815 RingCT/type: yes/0
Extra: 01e1aea84f3d4cb55c104db13ee39274fd6e551053af5a78531c13bbfb2aa8ceae0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f84a2e1f9ca2eb129fef1ce943fdcdbc391163c7bc93f77f8c5480cce36800b9 0.600000000000 1679649 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": 1193100, "vin": [ { "gen": { "height": 1193090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f84a2e1f9ca2eb129fef1ce943fdcdbc391163c7bc93f77f8c5480cce36800b9" } } ], "extra": [ 1, 225, 174, 168, 79, 61, 76, 181, 92, 16, 77, 177, 62, 227, 146, 116, 253, 110, 85, 16, 83, 175, 90, 120, 83, 28, 19, 187, 251, 42, 168, 206, 174, 2, 17, 0, 0, 0, 2, 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