Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b487e544a233df206a004f690bfdd3b415dbe005ecd4381d63541144808d38f3

Tx prefix hash: 62e446a1432afc45d44c144fa5760e5301e19f350a5fff0a984b88e4856ef53f
Tx public key: c5bb4e80ae1d7e4626e389aac912895235b959358e009fa586c942aa0b7416a4
Timestamp: 1694817661 Timestamp [UCT]: 2023-09-15 22:41:01 Age [y:d:h:m:s]: 01:261:09:00:39
Block: 848970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447942 RingCT/type: yes/0
Extra: 01c5bb4e80ae1d7e4626e389aac912895235b959358e009fa586c942aa0b7416a402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.944082666000 dcy

stealth address amount amount idx
00: d4baf42f7f90cbad1d980091e49e84d71879d2b2a9d22f019b944eb234736e76 0.944082666000 1302606 of 0

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": 848980, "vin": [ { "gen": { "height": 848970 } } ], "vout": [ { "amount": 944082666, "target": { "key": "d4baf42f7f90cbad1d980091e49e84d71879d2b2a9d22f019b944eb234736e76" } } ], "extra": [ 1, 197, 187, 78, 128, 174, 29, 126, 70, 38, 227, 137, 170, 201, 18, 137, 82, 53, 185, 89, 53, 142, 0, 159, 165, 134, 201, 66, 170, 11, 116, 22, 164, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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