Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec76f0695e6a41fb1031ec37bc996974cce11c4b1f38d4cfe462e68040c34fd3

Tx prefix hash: 1ac03defcc22973b2d6d5996ab06876e3f69c156905db26db2e77a84105d7c11
Tx public key: 79252566e067eeebcd8b953f308c186fdf0aeb3e21722f4e1377aec93351c934
Timestamp: 1721445742 Timestamp [UCT]: 2024-07-20 03:22:22 Age [y:d:h:m:s]: 00:238:01:29:34
Block: 1069581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170026 RingCT/type: yes/0
Extra: 0179252566e067eeebcd8b953f308c186fdf0aeb3e21722f4e1377aec93351c934021100000003162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc39d7065f892470ae291c85f68eafb10ec71215979c29e5c507e5e054f45c87 0.600000000000 1541054 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": 1069591, "vin": [ { "gen": { "height": 1069581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc39d7065f892470ae291c85f68eafb10ec71215979c29e5c507e5e054f45c87" } } ], "extra": [ 1, 121, 37, 37, 102, 224, 103, 238, 235, 205, 139, 149, 63, 48, 140, 24, 111, 223, 10, 235, 62, 33, 114, 47, 78, 19, 119, 174, 201, 51, 81, 201, 52, 2, 17, 0, 0, 0, 3, 22, 38, 19, 170, 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