Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f464f020c33dcce64c0a442f5df8440745e664d96f0a93d3706241847903a48

Tx prefix hash: ebf15a2e40f57916249096f5ae46507e9a140f7ce0292438487452d9a9b6c40e
Tx public key: 523e868d8442c4f2d149d95aa0fdd1029b3166f8b99c067e197363bed76d8b28
Timestamp: 1724211897 Timestamp [UCT]: 2024-08-21 03:44:57 Age [y:d:h:m:s]: 00:142:00:24:12
Block: 1092482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101577 RingCT/type: yes/0
Extra: 01523e868d8442c4f2d149d95aa0fdd1029b3166f8b99c067e197363bed76d8b28021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca57a6dea8bacb0781f8a8b35e10a590729e4ed5dc779a97e098b7177ce16ea9 0.600000000000 1567237 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": 1092492, "vin": [ { "gen": { "height": 1092482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca57a6dea8bacb0781f8a8b35e10a590729e4ed5dc779a97e098b7177ce16ea9" } } ], "extra": [ 1, 82, 62, 134, 141, 132, 66, 196, 242, 209, 73, 217, 90, 160, 253, 209, 2, 155, 49, 102, 248, 185, 156, 6, 126, 25, 115, 99, 190, 215, 109, 139, 40, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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