Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d5f9c1edda73cd96c57cb211e313edb0cff49c86d8c2860936d67be52f086ec

Tx prefix hash: bf214bc69fa91ddcc7711d74667b9c787dbb58ee0558f700551b008c7e6413d4
Tx public key: 6cefe92a4359eed6955445c7a18430d1a998fb84d27d1b4b94b075d0f361047e
Timestamp: 1735858041 Timestamp [UCT]: 2025-01-02 22:47:21 Age [y:d:h:m:s]: 00:321:18:40:00
Block: 1188897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227481 RingCT/type: yes/0
Extra: 016cefe92a4359eed6955445c7a18430d1a998fb84d27d1b4b94b075d0f361047e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e229b0736ad7821f3efecde50d7a5cbe76e6f0dc12affe389178cc5bef3c416 0.600000000000 1675402 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": 1188907, "vin": [ { "gen": { "height": 1188897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e229b0736ad7821f3efecde50d7a5cbe76e6f0dc12affe389178cc5bef3c416" } } ], "extra": [ 1, 108, 239, 233, 42, 67, 89, 238, 214, 149, 84, 69, 199, 161, 132, 48, 209, 169, 152, 251, 132, 210, 125, 27, 75, 148, 176, 117, 208, 243, 97, 4, 126, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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