Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b280d5cd37327339e0c18f0d2b8ea7740738f5cfd7768115d221839bfb608a04

Tx prefix hash: 2f31959a1d7b643adb1e2b56ab0ce4074160d494531df071867b649d596bedfe
Tx public key: f08cf5f63f57ca3c1dbe4716c4369ccdae72d65a6bec927cda60068be5b65e23
Timestamp: 1702416408 Timestamp [UCT]: 2023-12-12 21:26:48 Age [y:d:h:m:s]: 01:186:06:59:07
Block: 911797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394207 RingCT/type: yes/0
Extra: 01f08cf5f63f57ca3c1dbe4716c4369ccdae72d65a6bec927cda60068be5b65e23021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56e25d1d7950fac3f37d3b8e0fb88e33e1235ca01fd5dcd1d885b1e5fe147324 0.600000000000 1369013 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": 911807, "vin": [ { "gen": { "height": 911797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56e25d1d7950fac3f37d3b8e0fb88e33e1235ca01fd5dcd1d885b1e5fe147324" } } ], "extra": [ 1, 240, 140, 245, 246, 63, 87, 202, 60, 29, 190, 71, 22, 196, 54, 156, 205, 174, 114, 214, 90, 107, 236, 146, 124, 218, 96, 6, 139, 229, 182, 94, 35, 2, 17, 0, 0, 0, 3, 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