Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35661663fedbb0528c08928a64212e0d8d93524432d1c34ff37fb853484cc9b1

Tx prefix hash: 023f572986aa7d6abdc5835cf1beeb4d5c82712096773ecf313128858b8399f6
Tx public key: d77341c71d78399191774e6305f8c0028db5e6fb5df261589e921e61d9ed7576
Timestamp: 1726502202 Timestamp [UCT]: 2024-09-16 15:56:42 Age [y:d:h:m:s]: 00:069:02:53:08
Block: 1111463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49410 RingCT/type: yes/0
Extra: 01d77341c71d78399191774e6305f8c0028db5e6fb5df261589e921e61d9ed7576021100000001e914dd15000000000000000000

1 output(s) for total of 0.607980000000 dcy

stealth address amount amount idx
00: 5c423bdce63e68b6fd50b86c72f9548fee77a19475c5aa17c5a7fe243ed29261 0.607980000000 1590430 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": 1111473, "vin": [ { "gen": { "height": 1111463 } } ], "vout": [ { "amount": 607980000, "target": { "key": "5c423bdce63e68b6fd50b86c72f9548fee77a19475c5aa17c5a7fe243ed29261" } } ], "extra": [ 1, 215, 115, 65, 199, 29, 120, 57, 145, 145, 119, 78, 99, 5, 248, 192, 2, 141, 181, 230, 251, 93, 242, 97, 88, 158, 146, 30, 97, 217, 237, 117, 118, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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