Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc5fd5958cb09ce38b740e9db02db2a9b3dfefdaa927b0a53a656eeb45dbec3

Tx prefix hash: d8ca5805f7075e2b1e28ea189c1af38f237fb4e7bc7679390170e5b5b3846291
Tx public key: c39e88be41e91d5e5ab840f144372294a1b4446fd155dbdd172831b52210ad97
Timestamp: 1706328394 Timestamp [UCT]: 2024-01-27 04:06:34 Age [y:d:h:m:s]: 01:030:17:47:18
Block: 944186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283034 RingCT/type: yes/0
Extra: 01c39e88be41e91d5e5ab840f144372294a1b4446fd155dbdd172831b52210ad9702110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 181120f215019f7b1a372952f15aaeb319e921bbd05a58c6a61adc60e170e062 0.600000000000 1402422 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": 944196, "vin": [ { "gen": { "height": 944186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "181120f215019f7b1a372952f15aaeb319e921bbd05a58c6a61adc60e170e062" } } ], "extra": [ 1, 195, 158, 136, 190, 65, 233, 29, 94, 90, 184, 64, 241, 68, 55, 34, 148, 161, 180, 68, 111, 209, 85, 219, 221, 23, 40, 49, 181, 34, 16, 173, 151, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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