Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6dd348b8bcdcb2ff06cf1985185bf30352a9f88962cb53bb4e645cea65ddbf5

Tx prefix hash: 53b04624e7cb489841d2fe3dc4e33df5750de26814b0d6a15a887c6c7ad7c847
Tx public key: 40ba482163dbee7c98dce75316b588bd42efb0bbb27b7699c3f61b71b0273088
Timestamp: 1705150795 Timestamp [UCT]: 2024-01-13 12:59:55 Age [y:d:h:m:s]: 01:087:23:34:52
Block: 934432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323989 RingCT/type: yes/0
Extra: 0140ba482163dbee7c98dce75316b588bd42efb0bbb27b7699c3f61b71b02730880211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1ebac4a7b3a1beda1685b9ec5e90ae094635ea0712274ef0ddc362a6bb13ea9 0.600000000000 1392440 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": 934442, "vin": [ { "gen": { "height": 934432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1ebac4a7b3a1beda1685b9ec5e90ae094635ea0712274ef0ddc362a6bb13ea9" } } ], "extra": [ 1, 64, 186, 72, 33, 99, 219, 238, 124, 152, 220, 231, 83, 22, 181, 136, 189, 66, 239, 176, 187, 178, 123, 118, 153, 195, 246, 27, 113, 176, 39, 48, 136, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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