Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e91832ff26c295ba9c0aa1f4f3e3ef2b77984fd7a47cc9aaba39fbfd35f5bcf

Tx prefix hash: 820cea14fed1360ce346e479bddc352e31eab978a84d7665ca99de6da3af87a0
Tx public key: 0ddc87e2ada8709bbd3c70f15c46737c8f2748117eab4acd231bc1988457a4af
Timestamp: 1701874072 Timestamp [UCT]: 2023-12-06 14:47:52 Age [y:d:h:m:s]: 01:164:18:26:59
Block: 907281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378933 RingCT/type: yes/0
Extra: 010ddc87e2ada8709bbd3c70f15c46737c8f2748117eab4acd231bc1988457a4af02110000000439e1d5d3000000000000000000

1 output(s) for total of 0.605064105000 dcy

stealth address amount amount idx
00: 951d4ea1ab3efddf3563579f430b5feeeb9bd0217650332ec074486fb0820409 0.605064105000 1364264 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": 907291, "vin": [ { "gen": { "height": 907281 } } ], "vout": [ { "amount": 605064105, "target": { "key": "951d4ea1ab3efddf3563579f430b5feeeb9bd0217650332ec074486fb0820409" } } ], "extra": [ 1, 13, 220, 135, 226, 173, 168, 112, 155, 189, 60, 112, 241, 92, 70, 115, 124, 143, 39, 72, 17, 126, 171, 74, 205, 35, 27, 193, 152, 132, 87, 164, 175, 2, 17, 0, 0, 0, 4, 57, 225, 213, 211, 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