Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a2167135e118ae016c0f4881ca43171e5e844a7c91549e61cf7570fdee544b

Tx prefix hash: bac9dbba2ef1c157741df69877dbafa2c1c875f505114aa99d07134b1c558691
Tx public key: b18fbc179da80bf7ed9264500c5587a2c7dcb9ccda85b21a5b8f9cb1bbf94715
Timestamp: 1739047659 Timestamp [UCT]: 2025-02-08 20:47:39 Age [y:d:h:m:s]: 00:286:00:32:39
Block: 1215037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202180 RingCT/type: yes/0
Extra: 01b18fbc179da80bf7ed9264500c5587a2c7dcb9ccda85b21a5b8f9cb1bbf94715021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d6b16c8c05898963e31c9f5ef266db9c5b7dba39afa3885480986e1a8c5ead9 0.600000000000 1701834 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": 1215047, "vin": [ { "gen": { "height": 1215037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d6b16c8c05898963e31c9f5ef266db9c5b7dba39afa3885480986e1a8c5ead9" } } ], "extra": [ 1, 177, 143, 188, 23, 157, 168, 11, 247, 237, 146, 100, 80, 12, 85, 135, 162, 199, 220, 185, 204, 218, 133, 178, 26, 91, 143, 156, 177, 187, 249, 71, 21, 2, 17, 0, 0, 0, 2, 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