Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b7c5861a946c95aa035147c55f0e2214c2bc97c66e7ed0141b414937cd4df7d

Tx prefix hash: 7df03f134e0b6a07cfda42ca4c9f80e990ec798ed90686e3fcc90db52265e0b3
Tx public key: 2c60e278c743cd6c52c513eb4ac64290fd3e1b692cc1d596852ff3dbc4dab9a6
Timestamp: 1578800227 Timestamp [UCT]: 2020-01-12 03:37:07 Age [y:d:h:m:s]: 05:023:00:17:31
Block: 43615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166621 RingCT/type: yes/0
Extra: 012c60e278c743cd6c52c513eb4ac64290fd3e1b692cc1d596852ff3dbc4dab9a602110000014249b77a3d000000000000000000

1 output(s) for total of 440.034007681000 dcy

stealth address amount amount idx
00: 41c243fcabb2fc36e3dc2349cbadcc78d96c90972367af977b2d276b00a3ad5b 440.034007681000 79073 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": 43625, "vin": [ { "gen": { "height": 43615 } } ], "vout": [ { "amount": 440034007681, "target": { "key": "41c243fcabb2fc36e3dc2349cbadcc78d96c90972367af977b2d276b00a3ad5b" } } ], "extra": [ 1, 44, 96, 226, 120, 199, 67, 205, 108, 82, 197, 19, 235, 74, 198, 66, 144, 253, 62, 27, 105, 44, 193, 213, 150, 133, 47, 243, 219, 196, 218, 185, 166, 2, 17, 0, 0, 1, 66, 73, 183, 122, 61, 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