Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaeb98792fec8ed4c8c1f58768c5ea4f0bc405592b63471eb400be1afb137b2a

Tx prefix hash: 90a90cf260815bed3b90eb4d1fbf8aa08a6dce67f51cc1e8fe628eb9713c8cae
Tx public key: 658fd563a783be67be96864df84f679a57dca40661a0db0c185e5f37d7f99910
Timestamp: 1711571082 Timestamp [UCT]: 2024-03-27 20:24:42 Age [y:d:h:m:s]: 00:293:06:39:47
Block: 987689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209916 RingCT/type: yes/0
Extra: 01658fd563a783be67be96864df84f679a57dca40661a0db0c185e5f37d7f9991002110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 126f9eea8cc1bc5f48f2b72cd26ae9276bb0321a8ef0f3e413ecfb4bf72be4c8 0.600000000000 1447946 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": 987699, "vin": [ { "gen": { "height": 987689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "126f9eea8cc1bc5f48f2b72cd26ae9276bb0321a8ef0f3e413ecfb4bf72be4c8" } } ], "extra": [ 1, 101, 143, 213, 99, 167, 131, 190, 103, 190, 150, 134, 77, 248, 79, 103, 154, 87, 220, 164, 6, 97, 160, 219, 12, 24, 94, 95, 55, 215, 249, 153, 16, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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