Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2315b3f4d7a7430447dbb692e535e8feb6b6d2ff52736609cfeced93b6083e55

Tx prefix hash: 5e53f0abbc97c8af02f221e609444ed0fb71053191e1f24e8b946c65ec2499a6
Tx public key: 563fc9da80ee2995c3b3a8732a167dd99f32d0ff24768ddf8044750df5e216ac
Timestamp: 1700760482 Timestamp [UCT]: 2023-11-23 17:28:02 Age [y:d:h:m:s]: 01:206:14:40:13
Block: 898050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408765 RingCT/type: yes/0
Extra: 01563fc9da80ee2995c3b3a8732a167dd99f32d0ff24768ddf8044750df5e216ac0211000000044b8f5122000000000000000000

1 output(s) for total of 0.649213494000 dcy

stealth address amount amount idx
00: 9a3c21e525b63d4748c76d16d1252cac3468759edcdc50e8577885ce8c87e33a 0.649213494000 1354453 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": 898060, "vin": [ { "gen": { "height": 898050 } } ], "vout": [ { "amount": 649213494, "target": { "key": "9a3c21e525b63d4748c76d16d1252cac3468759edcdc50e8577885ce8c87e33a" } } ], "extra": [ 1, 86, 63, 201, 218, 128, 238, 41, 149, 195, 179, 168, 115, 42, 22, 125, 217, 159, 50, 208, 255, 36, 118, 141, 223, 128, 68, 117, 13, 245, 226, 22, 172, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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