Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4067dfdb895f9639aa71de067956dec34f842e2d457c59c1f2fc12dd4f7e33dd

Tx prefix hash: 0aa3cf0d2ce8b7489f654453829f1d31c85ec719fa7c7d155f145b1367bff94b
Tx public key: f1f4c2770148db0c656ceccedad4f4b44ff8157d8076df72ed3df3fad6bb4d21
Timestamp: 1738172706 Timestamp [UCT]: 2025-01-29 17:45:06 Age [y:d:h:m:s]: 00:144:05:37:40
Block: 1207806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102941 RingCT/type: yes/0
Extra: 01f1f4c2770148db0c656ceccedad4f4b44ff8157d8076df72ed3df3fad6bb4d21021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc6d63bbdd446b991e79ef7aecd4110d06205d412894b21bdb08c4fadc08bd40 0.600000000000 1694531 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": 1207816, "vin": [ { "gen": { "height": 1207806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc6d63bbdd446b991e79ef7aecd4110d06205d412894b21bdb08c4fadc08bd40" } } ], "extra": [ 1, 241, 244, 194, 119, 1, 72, 219, 12, 101, 108, 236, 206, 218, 212, 244, 180, 79, 248, 21, 125, 128, 118, 223, 114, 237, 61, 243, 250, 214, 187, 77, 33, 2, 17, 0, 0, 0, 5, 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