Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0722599980af86744a77c0b952378c8d9431cec79affd2906f6e8ed33df27d

Tx prefix hash: b0b5be40866916efbae61cf17bf1186d7d7b9fcddae9c76f48dcc7fe9fb8f728
Tx public key: 4974746e65dad1f0c4f52530afa2b2c09b8a3b687079645741d9cf79a3153f8d
Timestamp: 1735380133 Timestamp [UCT]: 2024-12-28 10:02:13 Age [y:d:h:m:s]: 00:170:01:35:56
Block: 1184935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121275 RingCT/type: yes/0
Extra: 014974746e65dad1f0c4f52530afa2b2c09b8a3b687079645741d9cf79a3153f8d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8346e94cc8b4766580c6817967c8d17dca3723e371cf5cd1f7872a0f493b7016 0.600000000000 1671398 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": 1184945, "vin": [ { "gen": { "height": 1184935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8346e94cc8b4766580c6817967c8d17dca3723e371cf5cd1f7872a0f493b7016" } } ], "extra": [ 1, 73, 116, 116, 110, 101, 218, 209, 240, 196, 245, 37, 48, 175, 162, 178, 192, 155, 138, 59, 104, 112, 121, 100, 87, 65, 217, 207, 121, 163, 21, 63, 141, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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