Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ccd0819b989f510187d883392f02b213a784ab5a7ce937d487416ae76006f4d

Tx prefix hash: 37277236052adfa422a835bdfeadcd85f4d2f5777fa0f7d43fdd7b1f194d4bd7
Tx public key: 9947e37a59c52a3c6dfa6223f99ed37464d6ac19464e76afc09ee9ef90228268
Timestamp: 1694950252 Timestamp [UCT]: 2023-09-17 11:30:52 Age [y:d:h:m:s]: 01:165:16:44:15
Block: 850067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379477 RingCT/type: yes/0
Extra: 019947e37a59c52a3c6dfa6223f99ed37464d6ac19464e76afc09ee9ef9022826802110000000875e3f0e9000000000000000000

1 output(s) for total of 0.936214161000 dcy

stealth address amount amount idx
00: a989ef43490b37d0a61492e85e7997f3b18114dcb8e04332d0a8766a4d65ba94 0.936214161000 1303763 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": 850077, "vin": [ { "gen": { "height": 850067 } } ], "vout": [ { "amount": 936214161, "target": { "key": "a989ef43490b37d0a61492e85e7997f3b18114dcb8e04332d0a8766a4d65ba94" } } ], "extra": [ 1, 153, 71, 227, 122, 89, 197, 42, 60, 109, 250, 98, 35, 249, 158, 211, 116, 100, 214, 172, 25, 70, 78, 118, 175, 192, 158, 233, 239, 144, 34, 130, 104, 2, 17, 0, 0, 0, 8, 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