Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97c8a64c39373c263999561bb058af0b73b479c564c2d3f47ad470746e86d7f2

Tx prefix hash: 0f98772845419c57e0407ef472e6b81d312ddd6adbbb77e8752828d47148b331
Tx public key: cc458fa364c71ac21884566ebe30eae82040a2d62d5e89bfc8b051e6d7f111be
Timestamp: 1705973933 Timestamp [UCT]: 2024-01-23 01:38:53 Age [y:d:h:m:s]: 00:341:13:52:01
Block: 941238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244568 RingCT/type: yes/0
Extra: 01cc458fa364c71ac21884566ebe30eae82040a2d62d5e89bfc8b051e6d7f111be02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d4e4ce64f453f5ac951c211ec2890f838e8d81423a7c0e0fc8854160fd83f5a 0.600000000000 1399384 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": 941248, "vin": [ { "gen": { "height": 941238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d4e4ce64f453f5ac951c211ec2890f838e8d81423a7c0e0fc8854160fd83f5a" } } ], "extra": [ 1, 204, 69, 143, 163, 100, 199, 26, 194, 24, 132, 86, 110, 190, 48, 234, 232, 32, 64, 162, 214, 45, 94, 137, 191, 200, 176, 81, 230, 215, 241, 17, 190, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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