Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c1e64bcea7b23fe72ded7f6cca35bfec6e56f431dd3fb34dd440ff3ac72eaf9

Tx prefix hash: af3a3ad7ebe03e89e679f08a8ab2d414b827e2a27360392eb58f7e911c77122c
Tx public key: b63b05515118495cd1cf4a034a8f912241a5a5fcf5a2b3768c2a717126d229a6
Timestamp: 1735710882 Timestamp [UCT]: 2025-01-01 05:54:42 Age [y:d:h:m:s]: 00:163:05:33:50
Block: 1187665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116447 RingCT/type: yes/0
Extra: 01b63b05515118495cd1cf4a034a8f912241a5a5fcf5a2b3768c2a717126d229a6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b41897ce2b57dd65ac874e29249ef13d1085583c79c19546e28c1311d3d14abc 0.600000000000 1674158 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": 1187675, "vin": [ { "gen": { "height": 1187665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b41897ce2b57dd65ac874e29249ef13d1085583c79c19546e28c1311d3d14abc" } } ], "extra": [ 1, 182, 59, 5, 81, 81, 24, 73, 92, 209, 207, 74, 3, 74, 143, 145, 34, 65, 165, 165, 252, 245, 162, 179, 118, 140, 42, 113, 113, 38, 210, 41, 166, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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