Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c743e0f4c591511457856bc7bed4c33bd97f4f959c2d6c3f7467cc5e755c875b

Tx prefix hash: 0e8c1aa811b13d79d645859ea18691b00b18a84f1c539da037b8de9f085f5049
Tx public key: bdf60150844546ee970620f502f637bb0b38c4f83cecfc2145ac0c239a87ee37
Timestamp: 1722322647 Timestamp [UCT]: 2024-07-30 06:57:27 Age [y:d:h:m:s]: 00:078:16:30:26
Block: 1076814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56364 RingCT/type: yes/0
Extra: 01bdf60150844546ee970620f502f637bb0b38c4f83cecfc2145ac0c239a87ee3702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc00cbed79ba35abb90ce32f5f060fb5abe715ee1bd88a8b0e44d2da72d8f502 0.600000000000 1549355 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": 1076824, "vin": [ { "gen": { "height": 1076814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc00cbed79ba35abb90ce32f5f060fb5abe715ee1bd88a8b0e44d2da72d8f502" } } ], "extra": [ 1, 189, 246, 1, 80, 132, 69, 70, 238, 151, 6, 32, 245, 2, 246, 55, 187, 11, 56, 196, 248, 60, 236, 252, 33, 69, 172, 12, 35, 154, 135, 238, 55, 2, 17, 0, 0, 0, 3, 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