Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31ccd05c9691d3d20de2f427281f2e7dbb93106c098175382c9f9ea9b120f450

Tx prefix hash: f9c204618c940743945d99335211d5588420301d0351e352805f953a851a9c08
Tx public key: e81f7e178f4cdbd867bba8f22cfb4b748a17b43cf22cbc785b7536224661b5ac
Timestamp: 1716855870 Timestamp [UCT]: 2024-05-28 00:24:30 Age [y:d:h:m:s]: 00:317:03:57:09
Block: 1031503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226673 RingCT/type: yes/0
Extra: 01e81f7e178f4cdbd867bba8f22cfb4b748a17b43cf22cbc785b7536224661b5ac0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2d3c6124ab80446f503638c021d8404bd2e5c5a9d510b06f0755cd7baf5d93 0.600000000000 1499952 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": 1031513, "vin": [ { "gen": { "height": 1031503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2d3c6124ab80446f503638c021d8404bd2e5c5a9d510b06f0755cd7baf5d93" } } ], "extra": [ 1, 232, 31, 126, 23, 143, 76, 219, 216, 103, 187, 168, 242, 44, 251, 75, 116, 138, 23, 180, 60, 242, 44, 188, 120, 91, 117, 54, 34, 70, 97, 181, 172, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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