Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1943e10c1be0353dcf619175b79703f5a02d8885f233bc07567911a70f76c7

Tx prefix hash: c007b05e03c13ce496b27fce75596b1d4a353925d1c391a76b02e7633a5722c4
Tx public key: 3f8de9f91d0060f5d85575b944f10f7c477fa820320acb35ade1fceef5ea1318
Timestamp: 1635579177 Timestamp [UCT]: 2021-10-30 07:32:57 Age [y:d:h:m:s]: 03:195:23:11:54
Block: 363492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918354 RingCT/type: yes/0
Extra: 013f8de9f91d0060f5d85575b944f10f7c477fa820320acb35ade1fceef5ea13180211000000026e80e2c6000000000000000000

1 output(s) for total of 38.335445546000 dcy

stealth address amount amount idx
00: 35fa91ed4d78aada0b04f1e67fd0649b4a6a247998b8d862516de4c791425b53 38.335445546000 738754 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": 363502, "vin": [ { "gen": { "height": 363492 } } ], "vout": [ { "amount": 38335445546, "target": { "key": "35fa91ed4d78aada0b04f1e67fd0649b4a6a247998b8d862516de4c791425b53" } } ], "extra": [ 1, 63, 141, 233, 249, 29, 0, 96, 245, 216, 85, 117, 185, 68, 241, 15, 124, 71, 127, 168, 32, 50, 10, 203, 53, 173, 225, 252, 238, 245, 234, 19, 24, 2, 17, 0, 0, 0, 2, 110, 128, 226, 198, 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