Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea3c7a15d2e86cf94471e7de211e7780d53838242d1d7759f88ab3589cb334e

Tx prefix hash: e12a8ac62dd56999361e29bdde7a7cb8903cedd1fd5c29384f5a2bea418cd3a8
Tx public key: 04556f41886ca56d4f61460976deca4dc95c11b8a5216ff729a904d74ba641d0
Timestamp: 1704465283 Timestamp [UCT]: 2024-01-05 14:34:43 Age [y:d:h:m:s]: 01:083:04:53:14
Block: 928752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320574 RingCT/type: yes/0
Extra: 0104556f41886ca56d4f61460976deca4dc95c11b8a5216ff729a904d74ba641d00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575c78cddb2d8b34b1f74a9b4cef89a34d11aeb91c5e3d68fc45b49a122dd9a2 0.600000000000 1386614 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": 928762, "vin": [ { "gen": { "height": 928752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575c78cddb2d8b34b1f74a9b4cef89a34d11aeb91c5e3d68fc45b49a122dd9a2" } } ], "extra": [ 1, 4, 85, 111, 65, 136, 108, 165, 109, 79, 97, 70, 9, 118, 222, 202, 77, 201, 92, 17, 184, 165, 33, 111, 247, 41, 169, 4, 215, 75, 166, 65, 208, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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