Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f36fb5c1695a43da18ebe419316387643be0fadb224347f6546708ca3202334

Tx prefix hash: d2712c1b5502557195fd1fa7a074fde05b3ba6c16d47a9b382830c61cc77ba3f
Tx public key: 431c8c9cbea8901cf5efd7d4f0fab8a4120b90cd4c750825765ad19b07f5ab85
Timestamp: 1720871226 Timestamp [UCT]: 2024-07-13 11:47:06 Age [y:d:h:m:s]: 00:249:11:40:04
Block: 1064787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178247 RingCT/type: yes/0
Extra: 01431c8c9cbea8901cf5efd7d4f0fab8a4120b90cd4c750825765ad19b07f5ab85021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec3624de6133d01d2f942536236c9441cb06941d90acd0eb9fd4788599cc59c7 0.600000000000 1535326 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": 1064797, "vin": [ { "gen": { "height": 1064787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec3624de6133d01d2f942536236c9441cb06941d90acd0eb9fd4788599cc59c7" } } ], "extra": [ 1, 67, 28, 140, 156, 190, 168, 144, 28, 245, 239, 215, 212, 240, 250, 184, 164, 18, 11, 144, 205, 76, 117, 8, 37, 118, 90, 209, 155, 7, 245, 171, 133, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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