Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eb3b9d3995ece4d296a7f7f19b753d3e83020c2be441dcb01bc4a293b24e290

Tx prefix hash: d5f9088220f726e61b5b29f3da0483ed15e9aa67bc73c3b4c65a3e864f367ad5
Tx public key: 7b7fa8f65b6352be1d9635c2d593cf626e914594d287cf813b5aba7b826118f1
Timestamp: 1583451593 Timestamp [UCT]: 2020-03-05 23:39:53 Age [y:d:h:m:s]: 04:340:12:57:35
Block: 77046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137747 RingCT/type: yes/0
Extra: 017b7fa8f65b6352be1d9635c2d593cf626e914594d287cf813b5aba7b826118f102110000000fd81c26c0000000000000000000

1 output(s) for total of 340.969405963000 dcy

stealth address amount amount idx
00: 9bbdf57cbb992f37c25a49a7878e58b04be6c51e1bb31f83589dbd59e28a4064 340.969405963000 141866 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": 77056, "vin": [ { "gen": { "height": 77046 } } ], "vout": [ { "amount": 340969405963, "target": { "key": "9bbdf57cbb992f37c25a49a7878e58b04be6c51e1bb31f83589dbd59e28a4064" } } ], "extra": [ 1, 123, 127, 168, 246, 91, 99, 82, 190, 29, 150, 53, 194, 213, 147, 207, 98, 110, 145, 69, 148, 210, 135, 207, 129, 59, 90, 186, 123, 130, 97, 24, 241, 2, 17, 0, 0, 0, 15, 216, 28, 38, 192, 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