Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f0cbe07624a8920ee60a340fe656a96ad2b519830910383ccd1f455a716cd3

Tx prefix hash: 4f148998fb97c7adfa6e39c09e39ce9570950276e68317ec3ffe09b116148e3a
Tx public key: 4b6f00491db0d9b8bb6bd013498ddf67945e3cf0c01c2dd052d99a603918d0b2
Timestamp: 1737993400 Timestamp [UCT]: 2025-01-27 15:56:40 Age [y:d:h:m:s]: 00:143:09:43:35
Block: 1206328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102409 RingCT/type: yes/0
Extra: 014b6f00491db0d9b8bb6bd013498ddf67945e3cf0c01c2dd052d99a603918d0b20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ac91fb62d3c2c340000d610151e283a74b2b445d6dc2d1f9e9d6cf582f64349 0.600000000000 1693031 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": 1206338, "vin": [ { "gen": { "height": 1206328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ac91fb62d3c2c340000d610151e283a74b2b445d6dc2d1f9e9d6cf582f64349" } } ], "extra": [ 1, 75, 111, 0, 73, 29, 176, 217, 184, 187, 107, 208, 19, 73, 141, 223, 103, 148, 94, 60, 240, 192, 28, 45, 208, 82, 217, 154, 96, 57, 24, 208, 178, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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