Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e92f104db3e65122ed783c3ce98cba78f2b4e54e87ef30300ec77648f3c6ea

Tx prefix hash: 78957af7e104e50f0ba31c14a152d98429d120522cc74f9f891327964e057e0c
Tx public key: 18e67769b73b9aea87c8409a2b88e525c11f87f00c7f59549fafd75d427498e6
Timestamp: 1713152764 Timestamp [UCT]: 2024-04-15 03:46:04 Age [y:d:h:m:s]: 01:010:10:17:25
Block: 1000767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268433 RingCT/type: yes/0
Extra: 0118e67769b73b9aea87c8409a2b88e525c11f87f00c7f59549fafd75d427498e60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e54f4a72e61b3390917188c2f3a290f2dceaaad6f8b48ef5de38480ea3489fd 0.600000000000 1461267 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": 1000777, "vin": [ { "gen": { "height": 1000767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e54f4a72e61b3390917188c2f3a290f2dceaaad6f8b48ef5de38480ea3489fd" } } ], "extra": [ 1, 24, 230, 119, 105, 183, 59, 154, 234, 135, 200, 64, 154, 43, 136, 229, 37, 193, 31, 135, 240, 12, 127, 89, 84, 159, 175, 215, 93, 66, 116, 152, 230, 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