Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 835ee126146341b12d1008fd885044df69283d5eca25a52ac10a4ede8ed5f8af

Tx prefix hash: 417d57a491cdbcc4c6353a699e3feea1f3e3d6f7ed2974bfbc2cc557fd482ac7
Tx public key: b8353a92f7f4c1700a48b431c0621e42d814e8d04cf3b31f242b7980420d580b
Timestamp: 1733776739 Timestamp [UCT]: 2024-12-09 20:38:59 Age [y:d:h:m:s]: 00:190:05:57:21
Block: 1171673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135684 RingCT/type: yes/0
Extra: 01b8353a92f7f4c1700a48b431c0621e42d814e8d04cf3b31f242b7980420d580b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f1a4464498b7b15322f81161685324ea1c9473ac6b8a69132421997bb2765da 0.600000000000 1657458 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": 1171683, "vin": [ { "gen": { "height": 1171673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f1a4464498b7b15322f81161685324ea1c9473ac6b8a69132421997bb2765da" } } ], "extra": [ 1, 184, 53, 58, 146, 247, 244, 193, 112, 10, 72, 180, 49, 192, 98, 30, 66, 216, 20, 232, 208, 76, 243, 179, 31, 36, 43, 121, 128, 66, 13, 88, 11, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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