Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94c58f840cbcfeff4163f4f63c96eb94b54872d00648dc54275d23e696f1c04

Tx prefix hash: 149477e8b26a70deb53f4b0f9c640df45b2220a91907dcdf39f423055b25444f
Tx public key: 54566ce9390a99ea6d096b1de93b375ac2d9c959142a93184a530990a9e93ea7
Timestamp: 1722995677 Timestamp [UCT]: 2024-08-07 01:54:37 Age [y:d:h:m:s]: 00:077:18:46:27
Block: 1082387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55690 RingCT/type: yes/0
Extra: 0154566ce9390a99ea6d096b1de93b375ac2d9c959142a93184a530990a9e93ea702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94816e2ee9b529c2ef2802f99bcd1513ab83c5d1b8a13cb42bec5e253eab8624 0.600000000000 1556214 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": 1082397, "vin": [ { "gen": { "height": 1082387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94816e2ee9b529c2ef2802f99bcd1513ab83c5d1b8a13cb42bec5e253eab8624" } } ], "extra": [ 1, 84, 86, 108, 233, 57, 10, 153, 234, 109, 9, 107, 29, 233, 59, 55, 90, 194, 217, 201, 89, 20, 42, 147, 24, 74, 83, 9, 144, 169, 233, 62, 167, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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