Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28af4ada4384aa9da3c7f32f34918e3947c979ef1561083151b95b02b66aaef9

Tx prefix hash: b1a3d47e11a536df03e6777471b20dc5de404d4486c3b4359fccc9b10724e699
Tx public key: 0eb8e4892c8792d724bef6e58aff6bcdc255a01a4d3c609bc68b1acd7c25b8f7
Timestamp: 1732238087 Timestamp [UCT]: 2024-11-22 01:14:47 Age [y:d:h:m:s]: 00:002:00:26:02
Block: 1158925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1445 RingCT/type: yes/0
Extra: 010eb8e4892c8792d724bef6e58aff6bcdc255a01a4d3c609bc68b1acd7c25b8f7021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1b3c3e109fa186f4374a1acf1baef3c82080b742c17c0e7ba2230cf2daff690 0.600000000000 1644556 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": 1158935, "vin": [ { "gen": { "height": 1158925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1b3c3e109fa186f4374a1acf1baef3c82080b742c17c0e7ba2230cf2daff690" } } ], "extra": [ 1, 14, 184, 228, 137, 44, 135, 146, 215, 36, 190, 246, 229, 138, 255, 107, 205, 194, 85, 160, 26, 77, 60, 96, 155, 198, 139, 26, 205, 124, 37, 184, 247, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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