Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94a7f3b76da259e3752ee314ce0c2c397598f338ae668d556fb56c2930021d02

Tx prefix hash: 1c99b165c8f8ad31b27c9426e1cd971c43282ab3d9cd8ff1c74c5fe64916b917
Tx public key: 43a076361a48764619a8f550bcd9d4ec12473a4961f805b9473c342c1cbdf5ea
Timestamp: 1712114705 Timestamp [UCT]: 2024-04-03 03:25:05 Age [y:d:h:m:s]: 01:065:23:27:22
Block: 992148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308190 RingCT/type: yes/0
Extra: 0143a076361a48764619a8f550bcd9d4ec12473a4961f805b9473c342c1cbdf5ea0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0a2bb6b3cfa46068b69ce93d623ac5344bb30df51f7217be856a5dccea7a5df 0.600000000000 1452486 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": 992158, "vin": [ { "gen": { "height": 992148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0a2bb6b3cfa46068b69ce93d623ac5344bb30df51f7217be856a5dccea7a5df" } } ], "extra": [ 1, 67, 160, 118, 54, 26, 72, 118, 70, 25, 168, 245, 80, 188, 217, 212, 236, 18, 71, 58, 73, 97, 248, 5, 185, 71, 60, 52, 44, 28, 189, 245, 234, 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