Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02670f8895f3dd0918d303c88e781656f0ed5b96d511959a69354425df0a8af1

Tx prefix hash: 28d757694461a0cf0d15ef5f845e388d582af9c05108154e9a15b11a8209434f
Tx public key: 2a5aa27f9e1cee3844ff31fa813400b8adf717fb2c477fb7de7d7131d70cd9f3
Timestamp: 1582978486 Timestamp [UCT]: 2020-02-29 12:14:46 Age [y:d:h:m:s]: 05:001:14:25:21
Block: 74079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155420 RingCT/type: yes/0
Extra: 012a5aa27f9e1cee3844ff31fa813400b8adf717fb2c477fb7de7d7131d70cd9f302110000006ac71d3ff9000000000000000000

1 output(s) for total of 348.775781064000 dcy

stealth address amount amount idx
00: 2fb23bda03f069bae0aeaa3f833c10d630190e08cca6ce37804e3ba6c7680604 348.775781064000 136906 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": 74089, "vin": [ { "gen": { "height": 74079 } } ], "vout": [ { "amount": 348775781064, "target": { "key": "2fb23bda03f069bae0aeaa3f833c10d630190e08cca6ce37804e3ba6c7680604" } } ], "extra": [ 1, 42, 90, 162, 127, 158, 28, 238, 56, 68, 255, 49, 250, 129, 52, 0, 184, 173, 247, 23, 251, 44, 71, 127, 183, 222, 125, 113, 49, 215, 12, 217, 243, 2, 17, 0, 0, 0, 106, 199, 29, 63, 249, 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