Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15dd6bf77429dcece56f84e67c86e18768281d552075386ad5d1da14510b591d

Tx prefix hash: 1c3f7f545e1d7120c072bbb72223eb3f489e49fbd37e417d6f7cd9f3a6eae43e
Tx public key: 4a9ea9e820bb8e1d3f23afe51bfb05821b9903f0a838335b45ec25c4690f13aa
Timestamp: 1737832727 Timestamp [UCT]: 2025-01-25 19:18:47 Age [y:d:h:m:s]: 00:144:10:56:52
Block: 1205206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102948 RingCT/type: yes/0
Extra: 014a9ea9e820bb8e1d3f23afe51bfb05821b9903f0a838335b45ec25c4690f13aa021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c97026f5654f7ae3e09e4e284b7b33e4ec78e6bbf4e13b6e70a72f5f48fa8e6 0.600000000000 1691903 of 15

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": 1205216, "vin": [ { "gen": { "height": 1205206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c97026f5654f7ae3e09e4e284b7b33e4ec78e6bbf4e13b6e70a72f5f48fa8e6" } } ], "extra": [ 1, 74, 158, 169, 232, 32, 187, 142, 29, 63, 35, 175, 229, 27, 251, 5, 130, 27, 153, 3, 240, 168, 56, 51, 91, 69, 236, 37, 196, 105, 15, 19, 170, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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