Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e42f0d2211ee399cd444716fa2661f37677da81f8749d9a9101e92b6368f285

Tx prefix hash: 1f7cc232223cd8fd70d9f2f92e586674be612fe903508b5b934602f63c5bb95d
Tx public key: b95c0bcbf0cbdb04ad1da419c5df246567c9cbc32253d0542770d2c7e80a6540
Timestamp: 1731100663 Timestamp [UCT]: 2024-11-08 21:17:43 Age [y:d:h:m:s]: 00:220:22:53:20
Block: 1149506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157672 RingCT/type: yes/0
Extra: 01b95c0bcbf0cbdb04ad1da419c5df246567c9cbc32253d0542770d2c7e80a6540021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99cdae9dff60d49ee6979bcf7f6375d4a37197b4e570074952b43c0308215bb0 0.600000000000 1634601 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": 1149516, "vin": [ { "gen": { "height": 1149506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99cdae9dff60d49ee6979bcf7f6375d4a37197b4e570074952b43c0308215bb0" } } ], "extra": [ 1, 185, 92, 11, 203, 240, 203, 219, 4, 173, 29, 164, 25, 197, 223, 36, 101, 103, 201, 203, 195, 34, 83, 208, 84, 39, 112, 210, 199, 232, 10, 101, 64, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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