Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a4e189373286ca6573a518c1689039f8098b6324de762d94bb35d410b4f3473

Tx prefix hash: 613301a28f91b9f08eaf732ab7699c0233badbbcc5f9b7f554320b7e7412c39a
Tx public key: 12ecf3fba9af7a4d072d05e67cf5a4eed10d338b8ef17604281e6e3a8d614e20
Timestamp: 1706638783 Timestamp [UCT]: 2024-01-30 18:19:43 Age [y:d:h:m:s]: 01:061:07:18:53
Block: 946761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304888 RingCT/type: yes/0
Extra: 0112ecf3fba9af7a4d072d05e67cf5a4eed10d338b8ef17604281e6e3a8d614e2002110000000281d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a156eb883c4f9104a16891328f4b41af89e31021d3acd192cd73eea6b1156aaa 0.600000000000 1405101 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": 946771, "vin": [ { "gen": { "height": 946761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a156eb883c4f9104a16891328f4b41af89e31021d3acd192cd73eea6b1156aaa" } } ], "extra": [ 1, 18, 236, 243, 251, 169, 175, 122, 77, 7, 45, 5, 230, 124, 245, 164, 238, 209, 13, 51, 139, 142, 241, 118, 4, 40, 30, 110, 58, 141, 97, 78, 32, 2, 17, 0, 0, 0, 2, 129, 215, 29, 85, 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