Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc1eaa61eb902f07c838ab2397dd266c36d3e083339118144e8b8fbdf9ac5b3

Tx prefix hash: 1bd64257105b8633a22982ce3af6c8232ccfaf33cd59f1f92e7e2c0473b64afa
Tx public key: 3ff388ce2d9af6e67d6b02aea98710a9b016786d2f4255e11cd6620011bb4dc1
Timestamp: 1718646396 Timestamp [UCT]: 2024-06-17 17:46:36 Age [y:d:h:m:s]: 01:143:00:37:46
Block: 1046332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360774 RingCT/type: yes/0
Extra: 013ff388ce2d9af6e67d6b02aea98710a9b016786d2f4255e11cd6620011bb4dc102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e183fd01dcc1df71bccc15e370aea87d4295e4dfc2d763b2d982acb1dfce8995 0.600000000000 1516143 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": 1046342, "vin": [ { "gen": { "height": 1046332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e183fd01dcc1df71bccc15e370aea87d4295e4dfc2d763b2d982acb1dfce8995" } } ], "extra": [ 1, 63, 243, 136, 206, 45, 154, 246, 230, 125, 107, 2, 174, 169, 135, 16, 169, 176, 22, 120, 109, 47, 66, 85, 225, 28, 214, 98, 0, 17, 187, 77, 193, 2, 17, 0, 0, 0, 1, 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