Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31d2f5cd71ef359a8349e611e773f009b17bb8f166af8289b85b9d4e87ebaa44

Tx prefix hash: 8593e3993925c2fe1eaffa71f6c3e3100427ee14ec359b0d2302993e79bd046b
Tx public key: bf51ddf099e0482c01f8d59df2a458eeab4255131e893d143d67a1800eb0ae00
Timestamp: 1699923268 Timestamp [UCT]: 2023-11-14 00:54:28 Age [y:d:h:m:s]: 01:103:11:08:48
Block: 891115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335091 RingCT/type: yes/0
Extra: 01bf51ddf099e0482c01f8d59df2a458eeab4255131e893d143d67a1800eb0ae0002110000000775e3f0e9000000000000000000

1 output(s) for total of 0.684488383000 dcy

stealth address amount amount idx
00: 2c52487bf1c9644bcb5ae5a2cb97c3064941587a60f5ceb521cd0b04427b805b 0.684488383000 1347150 of 0

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": 891125, "vin": [ { "gen": { "height": 891115 } } ], "vout": [ { "amount": 684488383, "target": { "key": "2c52487bf1c9644bcb5ae5a2cb97c3064941587a60f5ceb521cd0b04427b805b" } } ], "extra": [ 1, 191, 81, 221, 240, 153, 224, 72, 44, 1, 248, 213, 157, 242, 164, 88, 238, 171, 66, 85, 19, 30, 137, 61, 20, 61, 103, 161, 128, 14, 176, 174, 0, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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