Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdda48a77394041be9289eb48a857cda4d6d96bde75f145be072fc38134028bb

Tx prefix hash: de97f45c2fd217d60f1390757fa522a341f02de5c6216a101c2e241258350e5b
Tx public key: 8aa23e8f0809d21ee4ac86c2089b6257db3f5ad769c3c33df940dfa7cfa88283
Timestamp: 1736921127 Timestamp [UCT]: 2025-01-15 06:05:27 Age [y:d:h:m:s]: 00:063:04:14:11
Block: 1197698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44941 RingCT/type: yes/0
Extra: 018aa23e8f0809d21ee4ac86c2089b6257db3f5ad769c3c33df940dfa7cfa88283021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9906bbf28431aba08aa702bf0c829e566247da160b9c31f1b891b2eeca5b6648 0.600000000000 1684311 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": 1197708, "vin": [ { "gen": { "height": 1197698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9906bbf28431aba08aa702bf0c829e566247da160b9c31f1b891b2eeca5b6648" } } ], "extra": [ 1, 138, 162, 62, 143, 8, 9, 210, 30, 228, 172, 134, 194, 8, 155, 98, 87, 219, 63, 90, 215, 105, 195, 195, 61, 249, 64, 223, 167, 207, 168, 130, 131, 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