Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c3076df22868175bc8be64876737ca0ddc3d6c99f69e6a696519c662778029b

Tx prefix hash: c2c28936fcb6df630e1d73e0378123234bad523b1a93ba46c0ad0f7fa22435f2
Tx public key: 1f48d7237695ae516d070297c207485b2487c6a2cb79d8020efaa093e279e582
Timestamp: 1582057049 Timestamp [UCT]: 2020-02-18 20:17:29 Age [y:d:h:m:s]: 04:349:00:33:47
Block: 67728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141588 RingCT/type: yes/0
Extra: 011f48d7237695ae516d070297c207485b2487c6a2cb79d8020efaa093e279e5820211000000334ac5aa02000000000000000000

1 output(s) for total of 366.091653699000 dcy

stealth address amount amount idx
00: 9eeeb86650999af7bbaecbbddcd88224b862d0e64c5e739ae2e6cd6d4cc11414 366.091653699000 124737 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": 67738, "vin": [ { "gen": { "height": 67728 } } ], "vout": [ { "amount": 366091653699, "target": { "key": "9eeeb86650999af7bbaecbbddcd88224b862d0e64c5e739ae2e6cd6d4cc11414" } } ], "extra": [ 1, 31, 72, 215, 35, 118, 149, 174, 81, 109, 7, 2, 151, 194, 7, 72, 91, 36, 135, 198, 162, 203, 121, 216, 2, 14, 250, 160, 147, 226, 121, 229, 130, 2, 17, 0, 0, 0, 51, 74, 197, 170, 2, 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