Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41a7b65888dbe94598f67551062a06d05ae37c63107f0c8d11d136c4c191bfb8

Tx prefix hash: 7c6d58f31abe474f509f7647945bd4750825809a98cb515b68df291ed6b54dca
Tx public key: 527785bd8950f032c9b4a64672e9e30098f259fcc04f0b6e69a94ad496b8702e
Timestamp: 1702185732 Timestamp [UCT]: 2023-12-10 05:22:12 Age [y:d:h:m:s]: 01:121:22:03:33
Block: 909873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348274 RingCT/type: yes/0
Extra: 01527785bd8950f032c9b4a64672e9e30098f259fcc04f0b6e69a94ad496b8702e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bbfe4e842e3058aa7870f5368f51e3664b4466cfe40c15e1f673e983bb72560 0.600000000000 1367000 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": 909883, "vin": [ { "gen": { "height": 909873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bbfe4e842e3058aa7870f5368f51e3664b4466cfe40c15e1f673e983bb72560" } } ], "extra": [ 1, 82, 119, 133, 189, 137, 80, 240, 50, 201, 180, 166, 70, 114, 233, 227, 0, 152, 242, 89, 252, 192, 79, 11, 110, 105, 169, 74, 212, 150, 184, 112, 46, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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