Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa55a362ed80727c21e1a0b33d7212f77d5755a7d5d7b9ca44a667fe0c3db41c

Tx prefix hash: 257034ee2ead02314b79f7f89d6986690c8990f606111b181391498ef0af2142
Tx public key: 57965d23cd374fd41cf13a6b9c8a1765b7a291eb4c1467ddfd526acda8435487
Timestamp: 1705642447 Timestamp [UCT]: 2024-01-19 05:34:07 Age [y:d:h:m:s]: 01:036:08:00:54
Block: 938502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287024 RingCT/type: yes/0
Extra: 0157965d23cd374fd41cf13a6b9c8a1765b7a291eb4c1467ddfd526acda84354870211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47952c7d2135c807cc7e2a248cfd8f4dd2da45adc4a5c3a78c6312f22a24be0c 0.600000000000 1396572 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": 938512, "vin": [ { "gen": { "height": 938502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47952c7d2135c807cc7e2a248cfd8f4dd2da45adc4a5c3a78c6312f22a24be0c" } } ], "extra": [ 1, 87, 150, 93, 35, 205, 55, 79, 212, 28, 241, 58, 107, 156, 138, 23, 101, 183, 162, 145, 235, 76, 20, 103, 221, 253, 82, 106, 205, 168, 67, 84, 135, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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