Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fb16a3f611ef3e43ed2af063eb4f9128920a10a12d8af404a1b3d9e079107c7

Tx prefix hash: e8471120c7734a9bf72c5a79166da011fc1b1335290e30b4b01bd18f3cd2d928
Tx public key: 1016300e2823ca5064a64a0bfe4191cb038512f87f02e724f0597a80c635b9da
Timestamp: 1728977933 Timestamp [UCT]: 2024-10-15 07:38:53 Age [y:d:h:m:s]: 00:001:15:52:30
Block: 1131991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1187 RingCT/type: yes/0
Extra: 011016300e2823ca5064a64a0bfe4191cb038512f87f02e724f0597a80c635b9da021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d254a33c2dee14ebfec9a10871015ab579c88b0df7d4ebf2170e131f402ee8e 0.600000000000 1614900 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": 1132001, "vin": [ { "gen": { "height": 1131991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d254a33c2dee14ebfec9a10871015ab579c88b0df7d4ebf2170e131f402ee8e" } } ], "extra": [ 1, 16, 22, 48, 14, 40, 35, 202, 80, 100, 166, 74, 11, 254, 65, 145, 203, 3, 133, 18, 248, 127, 2, 231, 36, 240, 89, 122, 128, 198, 53, 185, 218, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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