Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a884b25f773f197d1e91f2fddc5ad601eb8d7ccfa40bbb2bca0e64e4cc173d48

Tx prefix hash: cd0f8f337eef500d71081e9440299d556d607e54b41aef6d23c7619949970653
Tx public key: 2460fe01dfa459b69743f04913a2f39d2964b75129948fd89a9ec03bccd04ead
Timestamp: 1728181896 Timestamp [UCT]: 2024-10-06 02:31:36 Age [y:d:h:m:s]: 01:034:19:25:52
Block: 1125390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283261 RingCT/type: yes/0
Extra: 012460fe01dfa459b69743f04913a2f39d2964b75129948fd89a9ec03bccd04ead02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cce074b8e6b1e34cb307a2779ea4ea42d058a787ee4b0df1fad6eaf34fd8706e 0.600000000000 1608071 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": 1125400, "vin": [ { "gen": { "height": 1125390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cce074b8e6b1e34cb307a2779ea4ea42d058a787ee4b0df1fad6eaf34fd8706e" } } ], "extra": [ 1, 36, 96, 254, 1, 223, 164, 89, 182, 151, 67, 240, 73, 19, 162, 243, 157, 41, 100, 183, 81, 41, 148, 143, 216, 154, 158, 192, 59, 204, 208, 78, 173, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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