Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18bae1673e72b490041dcb54c1a5d15623527369e570b5be8ec5b42e6ce754d

Tx prefix hash: 6403a7df1c5ed4bdfab4fbd3e7084c6e15c33707397224eede16a79c313fb97d
Tx public key: 88c99a195391222a79fe5ca5ee441ae7889a7281af49d875f1e084d228bd7d79
Timestamp: 1676468701 Timestamp [UCT]: 2023-02-15 13:45:01 Age [y:d:h:m:s]: 02:089:01:16:11
Block: 697549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 585275 RingCT/type: yes/0
Extra: 0188c99a195391222a79fe5ca5ee441ae7889a7281af49d875f1e084d228bd7d7902110000000283600029000000000000000000

1 output(s) for total of 2.997302069000 dcy

stealth address amount amount idx
00: 84c72bc217e4437849fa43b9c05dc89a7e4f2c950b831d74b8d0c93eb132e7e6 2.997302069000 1140774 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": 697559, "vin": [ { "gen": { "height": 697549 } } ], "vout": [ { "amount": 2997302069, "target": { "key": "84c72bc217e4437849fa43b9c05dc89a7e4f2c950b831d74b8d0c93eb132e7e6" } } ], "extra": [ 1, 136, 201, 154, 25, 83, 145, 34, 42, 121, 254, 92, 165, 238, 68, 26, 231, 136, 154, 114, 129, 175, 73, 216, 117, 241, 224, 132, 210, 40, 189, 125, 121, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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