Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774cf8d4124b1c418dc8987cf1f81cb0897d80da79b3956f10b93742bbb16cc9

Tx prefix hash: 36b153073cd6a05630fd12c5e36452ee97ab68ccf60fb21401c4c6b599389542
Tx public key: b16d14066e2ed082fadaf8c8a6e0551d596a0a8f53e65d9cb030f613966766d2
Timestamp: 1721528243 Timestamp [UCT]: 2024-07-21 02:17:23 Age [y:d:h:m:s]: 00:251:09:08:03
Block: 1070222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179581 RingCT/type: yes/0
Extra: 01b16d14066e2ed082fadaf8c8a6e0551d596a0a8f53e65d9cb030f613966766d2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9551b41239d6d482d890d3a16adff71c4b0adfe28ab85ca56290f433729cc412 0.600000000000 1541967 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": 1070232, "vin": [ { "gen": { "height": 1070222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9551b41239d6d482d890d3a16adff71c4b0adfe28ab85ca56290f433729cc412" } } ], "extra": [ 1, 177, 109, 20, 6, 110, 46, 208, 130, 250, 218, 248, 200, 166, 224, 85, 29, 89, 106, 10, 143, 83, 230, 93, 156, 176, 48, 246, 19, 150, 103, 102, 210, 2, 17, 0, 0, 0, 4, 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