Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 402bd3aca2ad59e8915209331430dc43bd03905db573e46181931038cb81132a

Tx prefix hash: ce6108545d41fe30374b3fd9e085efad821b953befaf50555edbc0eb5b13df9f
Tx public key: 0e5938f6af98944fa7aa3d98b4d9c330a629ac62f8be58ade8bc6f8ac618e24e
Timestamp: 1639233223 Timestamp [UCT]: 2021-12-11 14:33:43 Age [y:d:h:m:s]: 02:343:00:17:46
Block: 393250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 763203 RingCT/type: yes/0
Extra: 010e5938f6af98944fa7aa3d98b4d9c330a629ac62f8be58ade8bc6f8ac618e24e021100000001408d5ef5000000000000000000

1 output(s) for total of 30.549201669000 dcy

stealth address amount amount idx
00: 50ac819e1db0b463ce721aa4fb60799fd9227d786a60b2386616756cca171ea7 30.549201669000 790437 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": 393260, "vin": [ { "gen": { "height": 393250 } } ], "vout": [ { "amount": 30549201669, "target": { "key": "50ac819e1db0b463ce721aa4fb60799fd9227d786a60b2386616756cca171ea7" } } ], "extra": [ 1, 14, 89, 56, 246, 175, 152, 148, 79, 167, 170, 61, 152, 180, 217, 195, 48, 166, 41, 172, 98, 248, 190, 88, 173, 232, 188, 111, 138, 198, 24, 226, 78, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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