Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b25fc333c60536e0f68fd329d5814c4772d454189304ac22224aa20fe46c9ca

Tx prefix hash: 1f3e861d446280e9d0c9443e41f2a06e4b051a86360cb77de42349758b516d4d
Tx public key: 1eb382d13b3712f98506e1fc10cb7dda4b7d32bf357b93812ee0e22e11d5ea76
Timestamp: 1738572086 Timestamp [UCT]: 2025-02-03 08:41:26 Age [y:d:h:m:s]: 00:288:00:35:36
Block: 1211094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203620 RingCT/type: yes/0
Extra: 011eb382d13b3712f98506e1fc10cb7dda4b7d32bf357b93812ee0e22e11d5ea76021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 411d404fa32c23220398b0f4cb875d897cac142452b8ab829348094bb7dd04e1 0.600000000000 1697853 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": 1211104, "vin": [ { "gen": { "height": 1211094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "411d404fa32c23220398b0f4cb875d897cac142452b8ab829348094bb7dd04e1" } } ], "extra": [ 1, 30, 179, 130, 209, 59, 55, 18, 249, 133, 6, 225, 252, 16, 203, 125, 218, 75, 125, 50, 191, 53, 123, 147, 129, 46, 224, 226, 46, 17, 213, 234, 118, 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