Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94e5db6b0cf2e3b37cfe2bb0fc75710599dc1b0005e9aad1b51c9d77d9ac260f

Tx prefix hash: f2a2656bf404d1dfde0dfdcbe597a2a8712c1725a46201ee3061bd2d9ebe9e1a
Tx public key: f4327930a7758fa0b6760b38c263e48aece17c59a6e6395e56bdb200361fade9
Timestamp: 1723535129 Timestamp [UCT]: 2024-08-13 07:45:29 Age [y:d:h:m:s]: 00:259:22:13:41
Block: 1086865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185672 RingCT/type: yes/0
Extra: 01f4327930a7758fa0b6760b38c263e48aece17c59a6e6395e56bdb200361fade902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2a47fecb1d762fa1bdbea1579d785e260758cf4f9df7730e4c4a4bd90c38ed5 0.600000000000 1561464 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": 1086875, "vin": [ { "gen": { "height": 1086865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2a47fecb1d762fa1bdbea1579d785e260758cf4f9df7730e4c4a4bd90c38ed5" } } ], "extra": [ 1, 244, 50, 121, 48, 167, 117, 143, 160, 182, 118, 11, 56, 194, 99, 228, 138, 236, 225, 124, 89, 166, 230, 57, 94, 86, 189, 178, 0, 54, 31, 173, 233, 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