Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3ff349fc600c110da1566520f45d57ec1c52b9da9f49f33df9c60201841b11

Tx prefix hash: fbe10641d9dcd49899ed788888ce9b115837a0831af6ff83f7bb6af2537bd5f7
Tx public key: 7b2d76b97db3f9cf81b325e9a87f88d53fa6286eacbaf7115687ac4cca5e4f61
Timestamp: 1704981499 Timestamp [UCT]: 2024-01-11 13:58:19 Age [y:d:h:m:s]: 01:303:20:05:46
Block: 933033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475974 RingCT/type: yes/0
Extra: 017b2d76b97db3f9cf81b325e9a87f88d53fa6286eacbaf7115687ac4cca5e4f6102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f76ea2cc0f1cedaf50b569067d8d6477ad5a701e3f4ff46e505a822c3f85bb8b 0.600000000000 1390977 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": 933043, "vin": [ { "gen": { "height": 933033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f76ea2cc0f1cedaf50b569067d8d6477ad5a701e3f4ff46e505a822c3f85bb8b" } } ], "extra": [ 1, 123, 45, 118, 185, 125, 179, 249, 207, 129, 179, 37, 233, 168, 127, 136, 213, 63, 166, 40, 110, 172, 186, 247, 17, 86, 135, 172, 76, 202, 94, 79, 97, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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