Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4824923d76dc43c95b080a5082d839e2fd3703702cd2bef300f108b91942c9c

Tx prefix hash: 9200f1d622fd5cb0ebc22de0aa316895fad7654db3c5fcb09d348c38c060340d
Tx public key: 27e0ae1d136eb17b8f2c83fb12fb451afafb8d13deb376e3b4052c57e994a97c
Timestamp: 1684886542 Timestamp [UCT]: 2023-05-24 00:02:22 Age [y:d:h:m:s]: 02:025:16:19:11
Block: 766699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540361 RingCT/type: yes/0
Extra: 0127e0ae1d136eb17b8f2c83fb12fb451afafb8d13deb376e3b4052c57e994a97c021100000004faf35c9c000000000000000000

1 output(s) for total of 1.768512443000 dcy

stealth address amount amount idx
00: 232ea38521e4fbcf3a6764423e8f32fe8f474538beaedcc477728c53fdcac1c6 1.768512443000 1215758 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": 766709, "vin": [ { "gen": { "height": 766699 } } ], "vout": [ { "amount": 1768512443, "target": { "key": "232ea38521e4fbcf3a6764423e8f32fe8f474538beaedcc477728c53fdcac1c6" } } ], "extra": [ 1, 39, 224, 174, 29, 19, 110, 177, 123, 143, 44, 131, 251, 18, 251, 69, 26, 250, 251, 141, 19, 222, 179, 118, 227, 180, 5, 44, 87, 233, 148, 169, 124, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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