Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 872fbfc33b3d2fa25a63e89c988f24bad7f29c1f52e97afb480d8fe7aa0d2cfc

Tx prefix hash: 674e3e670fc7784e6bc8019f48ba172cff4156168d751801c20363f4189ac609
Tx public key: 9f7a8599c267b475cc52d478b84934b81545b589abefdf1dfb8dab3679f04f69
Timestamp: 1728551275 Timestamp [UCT]: 2024-10-10 09:07:55 Age [y:d:h:m:s]: 00:107:20:59:59
Block: 1128449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77071 RingCT/type: yes/0
Extra: 019f7a8599c267b475cc52d478b84934b81545b589abefdf1dfb8dab3679f04f6902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fd7c3adec9ca88a014e0436df6b14a2e1a75ab8c30d83797571dd6ffdfa9ae6 0.600000000000 1611268 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": 1128459, "vin": [ { "gen": { "height": 1128449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd7c3adec9ca88a014e0436df6b14a2e1a75ab8c30d83797571dd6ffdfa9ae6" } } ], "extra": [ 1, 159, 122, 133, 153, 194, 103, 180, 117, 204, 82, 212, 120, 184, 73, 52, 184, 21, 69, 181, 137, 171, 239, 223, 29, 251, 141, 171, 54, 121, 240, 79, 105, 2, 17, 0, 0, 0, 1, 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