Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0409ac8ff214a6f575e5d23f76706e1ba3c5b01a2bd3d195cffedde91744d048

Tx prefix hash: 08436144e7d6ad8052d756a4ddc46c123eacf891e36a0f9cac33275881716798
Tx public key: 8bf873a6dcf17fd09e8ecc693e3ed18dc9a6b4b712f1444b546967616dd8710b
Timestamp: 1646643726 Timestamp [UCT]: 2022-03-07 09:02:06 Age [y:d:h:m:s]: 02:322:17:39:03
Block: 453158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 750112 RingCT/type: yes/0
Extra: 018bf873a6dcf17fd09e8ecc693e3ed18dc9a6b4b712f1444b546967616dd8710b02110000000a2e6b1fd5000000000000000000

1 output(s) for total of 19.341925462000 dcy

stealth address amount amount idx
00: b6fdcb2c6d6f40b7b9908f9bc78ee634a8c341a43073c124116b64df2cc72103 19.341925462000 868583 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": 453168, "vin": [ { "gen": { "height": 453158 } } ], "vout": [ { "amount": 19341925462, "target": { "key": "b6fdcb2c6d6f40b7b9908f9bc78ee634a8c341a43073c124116b64df2cc72103" } } ], "extra": [ 1, 139, 248, 115, 166, 220, 241, 127, 208, 158, 142, 204, 105, 62, 62, 209, 141, 201, 166, 180, 183, 18, 241, 68, 75, 84, 105, 103, 97, 109, 216, 113, 11, 2, 17, 0, 0, 0, 10, 46, 107, 31, 213, 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