Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cbf26c167b91f7b7b0c0a35cc139481e6770e7605a86c401647fb03bca16985

Tx prefix hash: 62505780a95d9838877d0c7f5fd238528ab71ff0e199d0989a4a31d5875aac79
Tx public key: 2b7048e9b0c48552e6b4ebfad75bb198b86d1885783317b11ed5906479f23555
Timestamp: 1694302583 Timestamp [UCT]: 2023-09-09 23:36:23 Age [y:d:h:m:s]: 01:068:05:17:14
Block: 844691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310054 RingCT/type: yes/0
Extra: 012b7048e9b0c48552e6b4ebfad75bb198b86d1885783317b11ed5906479f2355502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.975412088000 dcy

stealth address amount amount idx
00: bb0d964683114f9f871c0e7f2bd0fd7fbd48a5bd7f79ce9a1955d2803559935a 0.975412088000 1298015 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": 844701, "vin": [ { "gen": { "height": 844691 } } ], "vout": [ { "amount": 975412088, "target": { "key": "bb0d964683114f9f871c0e7f2bd0fd7fbd48a5bd7f79ce9a1955d2803559935a" } } ], "extra": [ 1, 43, 112, 72, 233, 176, 196, 133, 82, 230, 180, 235, 250, 215, 91, 177, 152, 184, 109, 24, 133, 120, 51, 23, 177, 30, 213, 144, 100, 121, 242, 53, 85, 2, 17, 0, 0, 0, 2, 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