Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d1f59690aa541434ff7c83f69cd38d6d13a8c106155e6ac4ffdb213aff1c47b

Tx prefix hash: a0f5ca605eb0de1f60d6754c12a19b7f663876bd9344024bd1e4a00f2a0054e5
Tx public key: 7f2238e16ce5fc353fca4ff469b426aee0ed20d37202f8f9ca3df10b0175540b
Timestamp: 1729399439 Timestamp [UCT]: 2024-10-20 04:43:59 Age [y:d:h:m:s]: 00:174:22:46:31
Block: 1135477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124812 RingCT/type: yes/0
Extra: 017f2238e16ce5fc353fca4ff469b426aee0ed20d37202f8f9ca3df10b0175540b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a1ece91485cb9945d5c4cc671d0e928f7de9b0530550d28db2e34b252b50cf6 0.600000000000 1618814 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": 1135487, "vin": [ { "gen": { "height": 1135477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a1ece91485cb9945d5c4cc671d0e928f7de9b0530550d28db2e34b252b50cf6" } } ], "extra": [ 1, 127, 34, 56, 225, 108, 229, 252, 53, 63, 202, 79, 244, 105, 180, 38, 174, 224, 237, 32, 211, 114, 2, 248, 249, 202, 61, 241, 11, 1, 117, 84, 11, 2, 17, 0, 0, 0, 1, 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