Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a57adf953afb166169f1cdcc8b1debcc3376a7886ded178449f06f48d898907d

Tx prefix hash: 2a9a26d05cd079c948611bd1f35baa57bd660adde327ff8adea4bed1b9059e6a
Tx public key: c4fe5c2c9fca9ebd7fa6dc4e65548c8a5965529b66785d6a537b6032601080f0
Timestamp: 1723491693 Timestamp [UCT]: 2024-08-12 19:41:33 Age [y:d:h:m:s]: 00:216:15:18:41
Block: 1086501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154728 RingCT/type: yes/0
Extra: 01c4fe5c2c9fca9ebd7fa6dc4e65548c8a5965529b66785d6a537b6032601080f002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2a875aca536c2a4d7b48bb0bcc61e4bcbf3a2bda07c8efd72b878a155364c1 0.600000000000 1561098 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": 1086511, "vin": [ { "gen": { "height": 1086501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2a875aca536c2a4d7b48bb0bcc61e4bcbf3a2bda07c8efd72b878a155364c1" } } ], "extra": [ 1, 196, 254, 92, 44, 159, 202, 158, 189, 127, 166, 220, 78, 101, 84, 140, 138, 89, 101, 82, 155, 102, 120, 93, 106, 83, 123, 96, 50, 96, 16, 128, 240, 2, 17, 0, 0, 0, 1, 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