Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fef33423510e01a09f58cbe57dc6ad04b91fb267c643c25047f93bb81f314786

Tx prefix hash: c541edafabfa919b5017f91c43037055d2233182abd8bafed76e9479cf8db2f2
Tx public key: 2a7048ca3595f9f634dfabd9e5cfbf1ffa119585490e29b4b40c69347f8d7089
Timestamp: 1659167485 Timestamp [UCT]: 2022-07-30 07:51:25 Age [y:d:h:m:s]: 02:103:13:00:50
Block: 554832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595374 RingCT/type: yes/0
Extra: 012a7048ca3595f9f634dfabd9e5cfbf1ffa119585490e29b4b40c69347f8d70890211000000016570b1ef000000000000000000

1 output(s) for total of 8.904537915000 dcy

stealth address amount amount idx
00: 612c28c644c52f753f2c5e21b0f6366b057c4b7d06b5d25c6862e73553f46f2e 8.904537915000 986698 of 0

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": 554842, "vin": [ { "gen": { "height": 554832 } } ], "vout": [ { "amount": 8904537915, "target": { "key": "612c28c644c52f753f2c5e21b0f6366b057c4b7d06b5d25c6862e73553f46f2e" } } ], "extra": [ 1, 42, 112, 72, 202, 53, 149, 249, 246, 52, 223, 171, 217, 229, 207, 191, 31, 250, 17, 149, 133, 73, 14, 41, 180, 180, 12, 105, 52, 127, 141, 112, 137, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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