Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd2a2ec3e0280f445849a9ab0d7d3dd042ae4fe7dd2e1f05284decb2ddc13a8

Tx prefix hash: 95ce5826a25a9903ef3d752516f369a00d3231a18f1412eb033bf1bef23dd972
Tx public key: 475097806ed122bf7c089da630acb8117d07df9b940e3a16c7b778ecd61bcf30
Timestamp: 1738958368 Timestamp [UCT]: 2025-02-07 19:59:28 Age [y:d:h:m:s]: 00:353:04:17:03
Block: 1214301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250083 RingCT/type: yes/0
Extra: 01475097806ed122bf7c089da630acb8117d07df9b940e3a16c7b778ecd61bcf30021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43190d3af03cba0ca79e2d5343835bfff3e7ead6dbe5be151da923db724fe0da 0.600000000000 1701090 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": 1214311, "vin": [ { "gen": { "height": 1214301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43190d3af03cba0ca79e2d5343835bfff3e7ead6dbe5be151da923db724fe0da" } } ], "extra": [ 1, 71, 80, 151, 128, 110, 209, 34, 191, 124, 8, 157, 166, 48, 172, 184, 17, 125, 7, 223, 155, 148, 14, 58, 22, 199, 183, 120, 236, 214, 27, 207, 48, 2, 17, 0, 0, 0, 4, 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