Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b530d2ec13796c440d8eae12063a70ba6adfb6ca41c5ae740c8edec605397f4

Tx prefix hash: 9e3cd877a2d5636b4829a5cfe9595c3019b9072bdb73258d27109908e60a8ac6
Tx public key: b1e6d4453c1d727973e49eda36327f571eb5619271be8329197ce9a13dee2eac
Timestamp: 1709531774 Timestamp [UCT]: 2024-03-04 05:56:14 Age [y:d:h:m:s]: 01:029:00:12:30
Block: 970774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281718 RingCT/type: yes/0
Extra: 01b1e6d4453c1d727973e49eda36327f571eb5619271be8329197ce9a13dee2eac0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 422cef11f8530b78d1022c8586b382ea369e6f3aa6f6e82c67280ec2b505fb9b 0.600000000000 1430635 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": 970784, "vin": [ { "gen": { "height": 970774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "422cef11f8530b78d1022c8586b382ea369e6f3aa6f6e82c67280ec2b505fb9b" } } ], "extra": [ 1, 177, 230, 212, 69, 60, 29, 114, 121, 115, 228, 158, 218, 54, 50, 127, 87, 30, 181, 97, 146, 113, 190, 131, 41, 25, 124, 233, 161, 61, 238, 46, 172, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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