Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce7b4a29205fe01cba83c01a8c6397d93ef8ccce98415601b01dee9ca88af476

Tx prefix hash: 3fbf3dd706956a9463f31f1136c3b0d1f5268d2cd8db579aad67ae5c6f633d18
Tx public key: 8278a8b86645f2dbf111922338fa1a167fe51c15992b561a73a300f36d08b3a3
Timestamp: 1700619245 Timestamp [UCT]: 2023-11-22 02:14:05 Age [y:d:h:m:s]: 01:149:00:34:22
Block: 896878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367686 RingCT/type: yes/0
Extra: 018278a8b86645f2dbf111922338fa1a167fe51c15992b561a73a300f36d08b3a302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.655044587000 dcy

stealth address amount amount idx
00: cd1cebd9b7a174ece83de7832ef05fe4b654b2a7938a32b3212a8dc2f0dc338c 0.655044587000 1353223 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": 896888, "vin": [ { "gen": { "height": 896878 } } ], "vout": [ { "amount": 655044587, "target": { "key": "cd1cebd9b7a174ece83de7832ef05fe4b654b2a7938a32b3212a8dc2f0dc338c" } } ], "extra": [ 1, 130, 120, 168, 184, 102, 69, 242, 219, 241, 17, 146, 35, 56, 250, 26, 22, 127, 229, 28, 21, 153, 43, 86, 26, 115, 163, 0, 243, 109, 8, 179, 163, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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